home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Desktop Special Edition 1.0
/
SGI Desktop Special Edition 1.0.iso
/
relnotes
/
patchSG0000700
/
ch1.z
/
ch1
Wrap
Text File
|
1995-09-11
|
12KB
|
331 lines
- 1 -
1. _P_a_t_c_h__S_G_0_0_0_0_7_0_0__R_e_l_e_a_s_e__N_o_t_e
This release note describes patch SG0000700 to IRIX 5.3 with
XFS.
1.1 _W_a_r_n_i_n_g
This patch changes the format of some of the data written to
the log of XFS file systems. Because of this and the fact
that XFS root file systems are not unmounted cleanly in the
system shutdown process, this patch must not be removed once
it has been installed and an XFS file system has been used
for the root file system. For non-root file systems, it
will be possible to remove the patch as long as the file
systems are unmounted cleanly before doing so. If these
restrictions are not followed and the patch is removed, it
will not be possible to mount the XFS file systems using the
kernel not containing the patch.
This means that if you have loaded this patch and have an
XFS root filesystem, the standard IRIX 5.3 with XFS
installation tools found on the IRIX 5.3 with XFS CD (p/n
813-0323-001) will not work properly. Specifially, the root
filesystem will not be able to be mounted. Therefore, it is
imperative that you save the installation tools that you
received with this patch for use at a later date. Note that
this restriction will be lifted at the next release of the
operating system.
1.2 _S_u_p_p_o_r_t_e_d__H_a_r_d_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch contains bug fixes for the following machine
types. The software cannot be installed on other
configurations:
+o Challenge and Onyx with R4400 processors
+o Crimson (4D/510)
+o PowerSeries (4D/120, 4D/2xx, 4D/3xx and 4D/4xx)
+o Indigo and Indigo2
+o Indy
1.3 _S_u_p_p_o_r_t_e_d__S_o_f_t_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch contains bug fixes for IRIX 5.3 with XFS. The
software cannot be installed on other configurations.
- 2 -
1.4 _B_u_g_s__F_i_x_e_d__b_y__P_a_t_c_h__S_G_0_0_0_0_7_0_0
This patch contains fixes for the following bugs in IRIX 5.3
with XFS. Bug numbers from Silicon Graphics bug tracking
system are included for reference.
+o There is a very slight chance that the kernel could
panic when an XFS file system becomes full (bug
254266).
+o The implementation of the Data Management API is
incomplete in 5.3 with XFS. This patch includes the
pieces which were missing (bug 258113).
+o XFS file systems with small block sizes perform badly
on operations which scan large numbers of inodes, e.g.
du or find. This patch alters XFS to use larger
buffers for reading, writing, and caching inodes in
small blocks size file systems (bug 259540).
+o A process reading from a file in an XFS file system
using direct I/O could panic the system if it reads
beyond the end of the file (bug 260200).
+o When it encounters an error, xfs_growfs (actually the
syssgi(XFS_FSOPERATIONS) code supporting it) leaves the
buffer for the disk block which encountered the error
locked. Any subsequent attempts to run xfs_growfs will
become stuck waiting for that buffer to be unlocked
(bug 261003). If this problem occurs using XLV to grow
the volume containing the file system, the fix for XLV
in patch 301 will very likely be required as well.
+o Processes trying to read an XFS file at a constant rate
will sometimes encounter delays in the time it takes
for a read to complete. This is due to interference
from the periodic file system sync process and a
problem with the file cache taking too much memory.
This patch fixes the sync problem, and the file cache
problem is fixed in patch 288 (bug 261228).
+o The xfs_check utility would core dump under certain
conditions on an unrecovered file system (bug 261860).
+o Performing a file create system call on an XFS file
system root directory or the ".." entry of an XFS
directory would cause the process to hang indefinitely.
Other processes trying to traverse that directory would
become hung as well (bug 263205).
- 3 -
+o The NFS server implementation in Irix did not return
any value in the microseconds field for the modify time
on the return from a getattr call (rfe 251693).
+o The XFS code can panic complaining that a log
reservation has come up short (bug 270243).
+o Doing an 'ls' of small XFS directories over NFS can
fail from some other companies' NFS clients. This
causes the directory to appear empty or for 'ls' to
return errors from those client machines (bug 260747).
+o When using DIRECT_IO to read an XFS file, where the
size of the file is not an even multiple of 512 bytes,
an error will occur when trying to read the last block
of the file. The read system call will return an error
or the process will hang (bug 274423).
+o After booting a new kernel with added or deleted
filesystems, NFS clients may get bogus filehandle or
stale filehandle messages. For example, adding the
NFS3 filesystem or deleting the efs filesystem can
cause the problem (bug 274345, 278660)
+o The DMAPI event state isn't cleared in the on-disk
inode when a file is removed. When an inode is reused,
the new file may already have DMAPI events enabled.
(bug 275732)
+o The file system might not recover correctly after a
crash.
+o Small, synchronous writes to an XFS file were
particularly slow. This has been fixed by reducing the
amount of unnecessary I/O done for each write (bug
268182).
+o The filesystem will crash the kernel when looking up an
entry in a corrupted directory. While directories are
not supposed to become corrupted, this can happen due
to disk failures or XFS recovery bugs. With this fix
references to such entries will return errors rather
than crashing the system (bug 271325).
+o If an NFS client performs a directory lookup using a
file which is not a directory, the system will crash or
return incorrect results. The problem is not possible
if the NFS client is an SGI machine running a recent
release (bug 278247).
- 4 -
+o The system could crash due to a race condition in the
XFS transaction code for managing kernel buffers (bug
252383).
+o Installing patch 538 caused direct I/O to XFS files to
stop working (bug 282906).
+o The filesystem will sometimes crash the kernel in the
xfs_trans_chunk_committed() routine (bug 283739).
+o Programs calling msync(2) or fsync(2) on files residing
in XFS filesystems would sometimes hang for up to 10
seconds before returning from the system call (bug
283854).
+o XFS can sometimes crash in the transaction code due to
a race condition in the log callback code (bug 275579).
+o XFS can sometimes appear to freeze up for no reason
(bug 285600).
+o XFS can become deadlocked when there is a very large
amount of inode update activity (bug 290906).
+o Writes to XFS files using direct I/O do not return
errors properly when something is wrong. Instead,
small random values are returned (bug 291541).
+o Doing direct I/O writes to a file with pending buffered
writes can cause the direct I/O writes to fail (bug
291544).
1.5 _S_u_b_s_y_s_t_e_m_s__I_n_c_l_u_d_e_d__i_n__P_a_t_c_h__S_G_0_0_0_0_7_0_0
This patch release includes these subsystems:
+o patchSG0000700.eoe2_sw.xfs
1.6 _I_n_s_t_a_l_l_a_t_i_o_n__I_n_s_t_r_u_c_t_i_o_n_s
Because you want to install only the patches for problems
you have encountered, patch software is not installed by
default. After reading the descriptions of the bugs fixed in
this patch (see Section 1.3), determine the patches that
meet your specific needs.
If, after reading Sections 1.1 and 1.2 of these release
notes, you are unsure whether your hardware and software
meet the requirements for installing a particular patch, run
_i_n_s_t.
- 5 -
Patch software is installed like any other Silicon Graphics
software product. Follow the instructions in your _S_o_f_t_w_a_r_e
_I_n_s_t_a_l_l_a_t_i_o_n _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e to bring up the miniroot
form of the software installation tools.
Follow these steps to select a patch for installation:
1. At the Inst>prompt, type
iiiinnnnssssttttaaaallllllll ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
2. Select the desired patches for installation.
3. Initiate the installation sequence. Type
IIIInnnnsssstttt>>>> ggggoooo
4. You may find that two patches have been marked as
incompatible. If this occurs, you must deselect one
of the patches.
IIIInnnnsssstttt>>>> kkkkeeeeeeeepppp ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
5. After completing the installation process, exit the
_i_n_s_t program by typing
IIIInnnnsssstttt>>>> qqqquuuuiiiitttt
To remove a patch, use the _v_e_r_s_i_o_n_s _r_e_m_o_v_e command as you
would for any other software subsystem. The removal process
reinstates the original version of software unless you have
specifically removed the patch history from your system.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeee ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
To keep a patch but increase your disk space, use the
_v_e_r_s_i_o_n_s _r_e_m_o_v_e_h_i_s_t command to remove the patch history.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeeehhhhiiiisssstttt ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.